Release 10.1A: OpenEdge Application Server:
Developing WebSpeed Applications

How tagrun.p interacts with the custom tag

As with the other utility procedures in the install-path/src/web/support directory (and referenced in the tagmap.dat file), the web.output trigger procedure for tagrun.p is run when the output-fields event procedure has been dispatched for a Web object.

The web.output trigger takes hWid and fieldDef as input parameters; where hWid is the widget handle to the WebSpeed fill-in field associated with the custom tag, and fieldDef is the HTML field definition that appears in the HTML file. The output procedure then runs tagparse.p to parse the field definition for a specified tag attribute (in this case, NAME or FILE), both of which are passed as input parameters. After parsing fieldDef, tagparse.p returns the attribute value.

If the value of the FILE attribute is “screenvalue”, the tagrun.p web.output trigger procedure retrieves the SCREEN-VALUE widget attribute of the fill-in field object associated with the tag and runs the specified procedure. This procedure then generates the HTML table.

If the value of the FILE attribute is a filename, then the tagrun.p web.output trigger procedure runs the specified procedure to generate an HTML table. If you do not specify a FILE attribute, then you must define a custom web.output control handler to generate the HTML table.